Systems and methods for charging and billing

ABSTRACT

A method includes receiving input at a user interface displayed by a wireless device, the wireless device configured to access a communication service. The method also includes determining, at a processor of the wireless device, usage profile-related information based at least in part on the input. The method further includes generating a message associated with the usage profile-related information, the message indicating that usage of the communication service is to be billed to a first billing account of a plurality of billing accounts associated with the wireless device. The method also includes sending the message from the wireless device via a wireless network and directed to a network element.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of and claims priority from U.S. patent application Ser. No. 12/179,922, now U.S. Pat. No. 9,064,275, filed Jul. 25, 2008 and entitled “SYSTEMS AND METHODS FOR CHARGING AND BILLING IN CONVERGED COMMUNICATION NETWORKS,” the content of which is expressly incorporated by reference herein in its entirety.

TECHNICAL FIELD

The present disclosure relates generally to charging and billing.

BACKGROUND

IMS (Internet Protocol Multimedia Subsystem) is a standardized service delivery architecture that provides IP-based mobile and fixed multimedia services to IMS subscribers. IMS allows operators of different network types with varying architecture to offer the same services to all of their subscribers.

IMS subscribers, typically, access an IMS network via an access network using a UE (User Equipment). A UE is a device that has IP connectivity and is capable of requesting an IP address from the IMS network. A UE negotiates QoS (Quality of Service) requirements and other capabilities during a communication session setup process. Typically, a UE can negotiate the media type, traffic direction, bit rate, packet size, and bandwidth, for example.

Each IMS subscriber can be assigned a Private User Identity by the home IMS operator. A Private User Identity can be in the format of a NAI (Network Access Identifier), such as “username@operator.com.” A Private User Identity can be used to identify a subscription and authenticate a subscription. Each Private User Identity can be associated with one or more PUIDs (Public User Identifications) that are allocated by the home IMS operator.

An IMS communications session includes session management control connections for session control signaling and media flow connections for media flow between two or more IMS subscribers. IMS subscribers can use a variety of IP-based services in a single communication session.

SUMMARY

According to one aspect of the present disclosure, a method for operating a usage data processing system in a converged communications network can include receiving usage data from one or more network elements. The usage data can be associated with one or more public user identifications that can be used to charge and bill for service provided to one or more users. The method can further include processing the usage data to generate a unified usage record. The method can further include sending the unified usage record to a charging system that is configured to charge for the service based upon the one or more public user identifications.

In some embodiments, the usage data can be unformatted usage data. In other embodiments, the usage data can be formatted in a charging data record format. In some embodiments, processing the usage data to generate the unified usage record can include preparing the usage data to be formatted in a unified usage record format and formatting the usage data into the unified usage record format. In some embodiments, the converged communications network is an IMS network and the one or more network elements are one or more IMS network elements. In some embodiments, the one or more public user identifications can be assigned to one or more persona profiles.

According to another aspect of the present disclosure, a method for operating a charging system in a converged communications network can include receiving a unified usage record from a usage data processing system. The unified usage record can include one or more public user identifications and usage data collected from one or more network elements and processed by the usage data processing system to generate the unified usage record. The method can further include generating a charge for the unified usage record and sending the charge to a billing system for billing the charge based upon the one or more public user identifications.

In some embodiments, generating the charge for the unified usage record can include generating the charge for the unified usage record based upon a charge rate. In some embodiments, the converged communications network is an IMS network and the one or more network elements is one or more IMS network elements. In some embodiments, the one or more public user identifications is assigned to one or more persona profiles.

According to another aspect of the present disclosure, a method for operating a billing system in a converged communications network can include receiving a charge from a charging system. The charge can identify one or more accounts are associated with one or more public user identifications that can be used to bill for service provided to one or more users. The method can further include applying the charge to the one or more accounts.

In some embodiments, the method can further include generating an invoice and sending the invoice to the one or more users, wherein the invoice reflect the charge. In some embodiments, the converged communications network is an IMS network. In some embodiments, the one or more public user identifications are assigned to one or more persona profiles.

According to another aspect of the present disclosure, a billing system for billing services provided in a converged communications network can include one or more processors and one or more memory in communication with the processor. The memory can be configured to store instructions, executable by the processor to receive a charge from a charging system. The charge can identify one or more accounts associated with one or more public user identifications that can be used to bill for service provided to one or more users. The memory can be further configured to store instructions to apply the charge to the one or more accounts.

In some embodiments, the billing system memory can be further configured to store instructions, executable by the processor to generate an invoice and send the invoice to the one or more users, wherein the invoice reflects the charge. In some embodiments, the converged communications network is an IMS network.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 schematically illustrates a portion of a communications network, according to some exemplary embodiments of the present disclosure.

FIG. 2 schematically illustrates a mobile device and components thereof for use in accordance with some exemplary embodiments of the present disclosure.

FIG. 3 schematically illustrates a usage data processing system and components thereof for use in accordance with some exemplary embodiments of the present disclosure.

FIG. 4 schematically illustrates a unified usage record, according to some exemplary embodiments of the present disclosure.

FIG. 5 schematically illustrates an account structure, according to some exemplary embodiments of the present disclosure.

FIG. 6 schematically illustrates a network architecture, according to some exemplary embodiments of the present disclosure.

FIG. 7 schematically illustrates a method for charging and billing based upon a public user identification, according to some exemplary embodiments of the present disclosure.

DETAILED DESCRIPTION

As required, detailed embodiments of the present disclosure are disclosed herein. It must be understood that the disclosed embodiments are merely exemplary examples of the disclosure that may be embodied in various and alternative forms, and combinations thereof. As used herein, the word “exemplary” is used expansively to refer to embodiments that serve as an illustration, specimen, model or pattern. The figures are not necessarily to scale and some features may be exaggerated or minimized to show details of particular components. In other instances, well-known components, systems, materials or methods have not been described in detail in order to avoid obscuring the present disclosure. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present disclosure.

Referring now to the drawings wherein like numerals represent like elements throughout the drawings, FIG. 1 illustrates a portion of a communications network 100, according to an exemplary embodiment of the present disclosure. The illustrated communications network 100 includes an IMS (Internet Protocol Multimedia Subsystem) network 102 that is accessible via a wireless access network 104, a circuit-switched access network 106, and a packet-switched access network 108 via one or more UEs (User Equipments) 110. For purposes of clarity and brevity, the access networks 104, 106, 108 and the IMS network 102 are presented as single networks, although this is not necessarily the case. In implementation, multiple wireless access networks 104, multiple circuit-switched access networks 106, and/or multiple packet-switched access networks 108 can be used to access one or more IMS networks 102. The access networks 104, 106, 108 and/or the IMS network(s) 102 can be operated by one or more network operators, carriers, or service providers, for example.

As used herein, a UE 110 can include a device that is capable of accessing the IMS network 102 via IP (Internet Protocol) or other packet-based protocol. The UE 110 can include, for example, a VoIP (Voice over IP) phone, SIP (Session Initiation Protocol) phone, a telephone, a mobile phone, a cellular phone, an IP television, a computer, a personal digital assistant, a facsimile machine, or other communications device that is capable of communicating with one or more of the access networks 104, 106, 108 to access the IMS network 102.

Generally, the UE 110 can include a transceiver for communicating with an access network 104, 106, 108 and a processor for executing instructions, such as to operate one or more applications stored in a memory. The memory can include a variety of computer readable media, including volatile media, non-volatile media, removable media, and non-removable media. The memory, for example, can be configured to store one or more persona profiles.

An IMS subscriber can be identified by a private user ID and one or more PUIDs (Public User Identifications) can be associated with the private user ID. A persona profile can be associated with a PUID that is allocated by the IMS network 102 operator, for example.

Multiple PUIDs can be mapped to a persona profile or multiple persona profiles can be mapped to a PUID. Multiple PUIDs that are associated with a single UE 110 can be used to bill different accounts for services accessed via the UE 110. A persona profile can be identified by an operator-assigned name or a subscriber-assigned name.

By way of example and not limitation, one persona profile can be named “work” and another persona profile can be named “personal.” The “work” persona profile can be associated with a first PUID, for example, PUID-A, and the “personal” persona profile can be associated with a second PUID, for example, PUID-B. An IMS subscriber can select the “work” persona profile stored on the UE 110 to notify the IMS network 102 to rate, charge, and bill an account that is associated with PUID-A. Likewise, if the IMS subscriber wants to charge a personal account for services, the IMS subscriber can select the “personal” persona profile to notify the IMS network 102 to rate, charge, and/or bill an account that is associated with the PUID-B.

By way of another example and not limitation, one or more IMS subscribers can share an IMS access line and/or UE 110 and can be billed separately based upon the persona profile (PUID) used to access the IMS network 102.

A PUID can be, for example, a SIP URI (Uniform Resource Identifier) or a TEL (Telephone) URL (Uniform Resource Locator). A PUID that includes a SIP URI can take the form of “sip:first.last@operator.com” where “first” is the first name of the user, “last” is the last name of the user, and “operator” is the IMS network 102 operator. A PUID that includes a TEL URL can represent a telephone number and can take the form of “tel:+1-555-555-2368.” A TEL URL can be formatted in accordance with any telephone numbering plan. A telephone number can be included in a SIP URI and can take the form of “sip:+1-555-555 2368@operator.com;user=phone.” A TEL URL can be required for interworking a PSTN telephone.

The IMS network 102 can be configured in accordance with 3GPP specifications, although this is not necessarily the case. The IMS network 102 provides IP-based mobile and fixed single media and multimedia communication services for the UEs 110. The IMS network 102 is access network 104, 106, 108 independent. Each of the access networks 104, 106, 108 can provide access to services offered via the IMS network 102.

A gateway 112 can include interworking functions to allow communication between circuit-switched networks, such as the circuit-switched access network 106, and the IMS network 102. For example, the gateway 112 can provide access for circuit-switched access networks 106, signaling networks, such as SS7 (Signaling System Number 7), and POTS (Plain Old Telephone Service) networks, such as a PSTN (Public Switched Telephone Network).

The illustrated IMS network 102 includes elements that provide data collection, data mediation, charging, rating, billing, and routing functions of the present disclosure. For the sake of brevity and clarity, 3GPP elements, such as a CSCF (Call Session Control Function), a HSS (Home Subscriber Server), an AS (Application Server), and other 3GPP elements, are not specifically illustrated so as not to obscure the present disclosure. It should be understood, however, that these and other elements can be included in the network elements 114.

The wireless access network 104 can provide access to the IMS network 102 via wireless technologies, such as, but not limited to, GSM (Global System for Mobile communications), CDMA (Code Division Multiple Access), UMTS (Universal Mobile Telecommunications System) network, and provide data communications via EDGE (Enhanced Data rate for Global Evolution), the HSPA (High-Speed Packet Access) protocol family, such as, HSDPA (High-Speed Downlink Packet Access), EUL (Enhanced Uplink) or otherwise termed HSUPA (High-Speed Uplink Packet Access), and HSPA+ (Evolved HSPA), for example. The wireless access network 104 is also compatible with future wireless technologies including, but not limited to, pre-4G and 4G standards, for example. Other wireless access technologies are contemplated. Accordingly, the UE 110 can be a mobile device, such as a mobile device 200 illustrated in FIG. 2, that is configured to operate using one or more of the aforementioned technologies.

The circuit-switched access network 106 can provide access to the IMS network 102 via circuit-switched technologies, such as POTS, for example. The circuit-switched access network 106 can communicate with the IMS network 102 via the gateway 112. A UE 110 in communication with the circuit-switched access network 106 can be a POTS telephone, for example.

The packet-switched access network 108 can provide access to the IMS network 102 via packet-switched technologies. The packet-switched access network 108 can include the Internet or other PDN (Public Data Network), for example. A UE 110 in communication with the packet-switched access network 108 can include a computer, an IP television, a VoIP telephone, a SIP telephone, or other UE 110, for example.

The illustrated IMS network 102 includes a gateway 112, as described above, one or more network elements 114, one or more UDPSs (Usage Data Processing Systems) 116, one or more charging and rating systems 118, one or more routers 120, and one or more billing systems 122. Each of the IMS network 102 elements and systems are now described.

The one or more network elements 114 can include, but is not limited to, P-CSCFs (Proxy Call Session Control Functions), I-CSCFs (Interrogating Call Session Control Functions), S-CSCFs (Serving Call Session Control Functions), BGCFs (Breakout Gateway Control Functions), MRFCs (Media Resource Control Functions), MGCFs (Media Gateway Control Functions), AS's (Application Servers) that can be used in a communication session. The one or more network elements 114 can send raw usage data directly to the UDPS 116. The UDPS 116 can process and format the raw usage data into a UUR (Unified Usage Record) format. An exemplary UUR 400 is illustrated and described in more detail below with reference to FIG. 4. Alternatively, the network elements 114 can include charging functions to collect charging information and generate CDRs (Charging Detail Records or Call Detail Records) based upon the charging information. The network elements 114 can send the CDRs to the UDPS 116 for processing and for formatting the CDRs into a UUR format. An exemplary UDPS 116 is described in more detail below with reference to FIG. 3.

The charging and rating system 118 can include one or more rating modules and one or more charging modules. Rating modules can rate transactions based upon the service type(s) provided by the IMS network 102. Transactions can include multiple service segments and each service segment can be rated differently. Charging modules can generate charges based upon the rate provided by rating modules. The charging and rating system 118 can send the charge to a router 120. The router 120 can route the charge to the appropriate billing system 122 based upon routing rules used to analyze the PUID and to send the charge to the billing system 122 that performs billing functions for the IMS subscriber account that is associated with the PUID.

FIG. 2 is a schematic block diagram illustrating an exemplary mobile device 200 for use in accordance with some exemplary embodiments of the present disclosure. Although no connections are shown between the components illustrated and described in FIG. 2, the components can interact with each other to carry out device functions.

As illustrated, the mobile device 200 can be a multimode handset. FIG. 2 and the following discussion are intended to provide a brief, general description of a suitable environment in which the various aspects of some embodiments of the present disclosure can be implemented. While the description includes a general context of computer-executable instructions, the present disclosure can also be implemented in combination with other program modules and/or as a combination of hardware and software. The mobile device 200 is an example of one UE 110 that could be used to access the wireless access network 104, however, components described herein with reference to the mobile device 200 can be applicable to other UE types, such as a computer, IP television, VoIP telephone, SIP phone, and the like. As such, the description of the mobile device 200 is intended to apply to other UE types, where applicable.

Generally, applications can include routines, program modules, programs, components, data structures, and the like. Applications can be implemented on various system configurations, including single-processor or multiprocessor systems, minicomputers, mainframe computers, personal computers, hand-held computing devices, microprocessor-based, programmable consumer electronics, combinations thereof, and the like. The present disclosure can include application for selecting and accessing persona profiles stored on the UE 110.

The illustrated mobile device 200 includes a display 202 for displaying multimedia, such as, for example, text, images, video, telephony functions, caller line ID data, setup functions, menus, music metadata, messages, wallpaper, graphics, persona profiles, and the like. The device 200 can include a processor 204 for controlling, processing data, and/or executing instructions stored in a memory 206. The memory 206 can interface with the processor 204 for the storage of data and/or applications 208. The memory 206 can include a variety of computer readable media, including volatile media, non-volatile media, removable media, and non-removable media. Computer-readable media can include device storage media and communication media. Storage media can include volatile and/or non-volatile, removable and/or non-removable media, such as, for example, RAM, ROM, EEPROM, flash memory or other memory technology, CD ROM, DVD, or other optical disk storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and that can be accessed by the device 200.

The memory 206 can be configured to store one or more applications 208. The applications 208 can include a user interface (UI) application 210. The UI application 210 can interface with a client 212 (e.g., an operating system) to facilitate user interaction with device functionality and data, for example, selecting persona profiles, managing persona profiles, answering/initiating calls, entering/deleting data, configuring settings, address book manipulation, multimode interaction, music interaction, video interaction, and the like. The applications 208 can include other applications 214 such as, for example, persona profile software, add-ons, plug-ins, voice recognition software, call voice processing, voice recording, messaging software, e-mail software, video processing software, image processing software, music playback software, combinations thereof, and the like, as well as subsystems and/or components. The applications 208 can be stored in the memory 206 and/or in a firmware 216, and can be executed by the processor 204. The firmware 216 can also store code for execution during initialization of the device 200. The memory 206, applications 208, and/or firmware 216 can be configured to store one or more PUIDs.

A communications component 218 can interface with the processor 204 to facilitate wired/wireless communications with external systems including, for example, the wireless access network 104, the circuit-switched access network 106, and/or the packet-switched access network 108. The communications component 218 can generally provide access to cellular networks, VoIP networks, LAN, WAN, MAN, PAN, that can be implemented using WiFi, WiMax, combinations and/or improvements thereof, and the like. The communications component 218 can also include a multimode communications subsystem for providing cellular communications via different cellular technologies. For example, a first cellular transceiver 220 can operate in one mode, for example, GSM, and an Nth transceiver 222 can operate in a different mode, for example UMTS. While only two transceivers 220, 222 are illustrated, it should be appreciated that a plurality of transceivers can be included. The communications component 218 can also include a transceiver 224 for unlicensed RF communications using technology such as, for example, WiFi, WiMAX, NFC, other RF and the like. The transceiver 224 can also be configured for line-of-sight technologies, such as, for example, infrared and IRDA. Although a single transceiver 224 is illustrated multiple transceivers for unlicensed RF and line-of-sight technologies are contemplated.

The communications component 218 can also facilitate communications reception from terrestrial radio networks, digital satellite radio networks, Internet-based radio services networks, combinations thereof, and the like. The communications component 218 can process data from a packet-based access network 108, such as, for example, the Internet, a corporate intranet, a home broadband network, and the like, via an ISP, DSL provider, or other broadband service provider.

An input/output (I/O) interface 226 can be provided for input/output of data and/or signals. The I/O interface 226 can be a hardwire connection, such as, for example, a USB, PS2, IEEE 1394, serial, parallel, IEEE 802.3 (e.g., Ethernet—RJ45, RJ48), traditional telephone jack (e.g., RJ11, RJ14, RJ25) and the like, and can accept other I/O devices, such as, for example, a keyboard, keypad, mouse, interface tether, stylus pen, printer, plotter, jump/thumb drive, touch screen, touch pad, trackball, joy stick, controller, monitor, display, LCD, combinations thereof, and the like. The I/O interface 226 can be used to select a persona profile.

Audio capabilities can be provided by an audio I/O component 228 that can include a speaker (not shown) for the output of audio signals and a microphone (not shown) to collect audio signals.

The device 200 can include a slot interface 230 for accommodating a subscriber identity system 232, such as, for example, a SIM or universal SIM (USIM). The subscriber identity system 232 instead can be manufactured into the device 200, thereby obviating the need for a slot interface 230.

The device 200 can include an image capture and processing system 234. Photos and/or videos can be obtained via an associated image capture subsystem of the image system 234, for example, a camera. The device 200 can also include a video systems component 236 for processing, recording, and/or transmitting video content.

A location component 238 can be included to send and/or receive signals, such as, for example, GPS data, assisted GPS data, triangulation data, combinations thereof, and the like. The device 200 can use the received data to identify its location or can transmit data used by other devices to determine the device 200 location.

The device 200 can include a power source 240 such as batteries and/or other power subsystem (AC or DC). The power source 240 can be single-use, continuous, or rechargeable. In the case of the latter, the power source 240 can interface with an external power system or charging equipment via a power I/O component 242.

Referring now to FIG. 3, a UDPS (Usage Data Processing System) 116 and components thereof are illustrated for use in accordance with some exemplary embodiments of the present disclosure. The UDPS 116 can be configured to collect, mediate, filter, correlate, combine, and/or format usage information and/or CDRs received from the network elements 114 to a UUR format. Accordingly, the illustrated UDPS 116 includes a collection module 300, a mediation module 302, a filtration module 304, a correlation module 306, a combiner module 308, and a format module 310 that can perform corresponding functions for the UDPS 116 to create a UUR, such as a UUR 400 as illustrated in FIG. 4 and described below with reference thereto. Each module 302, 304, 306, 308, 310 can include a memory that is configured to store instructions, such as an algorithm, that can be executed by a processor to perform the corresponding functions. All or some of the modules may be needed to aggregate usage data into a UUR format. Alternatively, a single processor and memory system can be configured to perform some or all functions of the illustrated modules 300, 302, 304, 306, 308, 310.

The collection module 300 can be configured to collect raw usage data and/or usage date formatted in one or more CDRs received from the network elements 114. The mediation module 302 can be configured to convert data from one data format to another data format such that the data can be further processed. The filtration module 304 can be configured to filter usage data. The correlation module 306 can be configured to correlate usage data from multiple CDRs. The combiner module 308 can be configured to combine correlated usage data. The format module 310 can be configured to format the usage data into a UUR format, such as the UUR 400 described immediately below.

Referring now to FIG. 4, a UUR 400 is illustrated, according to an exemplary embodiment of the present disclosure. The illustrated UUR 400 includes a transaction ID field 402, a service type field 404, a PUID field 406, a device type field 408, a provider ID field 410, and an additional parameters field 412. It should be understood that some or all of the fields 402, 404, 406, 408, 410, 412 may be mandatory or optional.

The transaction ID field 402 can include a transaction ID that is used to correlate CDRs that are generated for the same transaction. For example, although different network elements 114 may be used in each service segment of a communication session, a unique transaction ID can identify each service segment as being associated with the same transaction.

The service type field 404 can include at least one service type that is used for a given transaction ID. For transactions that include multiple service segments and thus multiple service types, those service types can be listed in the service type field 404. A rating module can use the service type as one criterion for determining the charge rate for a given transaction ID.

The PUID field 406 can include the PUID used in the communication session that is to be rated, charged, and billed. The PUID can also be used to direct any charges identified for the UUR 400 to the IMS subscriber's account that is stored in one of the billing systems 122.

A device type in the device type field 408 can identify the device type of the UE 110 used in the communication session. A service may be rated differently based upon the device type used.

A provider ID in the provider ID field 410 can identify the service provider, operator, or third party that provides the service identified by the service type 404. Additional parameters 412 can be defined for a UUR 400 as determined by the service provider, an IMS subscriber, or third party, for example.

Referring now to FIG. 5, an account structure 500 is illustrated, according to some exemplary embodiments of the present disclosure. By the illustrated embodiment no limits or restrictions are imposed upon the number of bundled invoices, invoices, accounts, sub-accounts, service types, and/or persona profiles that can or should be used in any implementation of the present disclosure. Numerous bundled invoices, invoices, accounts, sub-accounts, service types, and/or persona profiles are contemplated.

The illustrated account structure 500 is presented as a hierarchical structure beginning with a hypothetical customer 502 who is an IMS subscriber. The customer 502 can operate one or more UEs 110 to access, via one or more access networks 104, 106, 108, services provided by the IMS network 102. A billing system, such as the billing system 122, can generate and send a bundled invoice 504 to the customer 502 via known invoice delivery methods, for example, mail, electronic mail, and/or a website. The bundled invoice 504 can include two or more invoices, illustrated as invoice A 506 and invoice B 508. Alternatively, separate invoices for invoice A 506 and invoice B 508 can be generated and sent to the customer 502. Each invoice 506, 508 can be associated with one or more accounts. In the illustrated example, account A 510 is associated with invoice A 506 and account B 512 is associated with invoice B 508. Account A 510 and account B 512 can be associated with one or more service accounts. By way of example and not limitation, account A 510 is described as a work account and account B 512 is described as a personal account that are each associated with the same customer 502.

The illustrated account A 510 branches to two sub-accounts, a first sub-account 514 and a second sub-account 516. It is contemplated that any number of sub-accounts can branch from an account or, alternatively, an account can branch directly to one or more service types and/or persona profiles. In the illustrated embodiment, however, the first sub-account 514 branches to two service types, a first service type 518 and a second service type 520, and to a first persona profile 522. The service types 518, 520 can be any fixed or mobile communications service provided by the IMS network 102. A persona profile can be associated with a PUID. In the illustrated embodiment, each service type 518, 520 can define a different service billed under the first sub-account 514. Also in the illustrated embodiment, the persona profile 522 can be viewed as a billable item for any services provided under that persona profile 522.

The illustrated second sub-account 516 branches to two service types, a third service type 524 and a fourth service type 526. It should be understood that the illustrated service types 518, 520, 524, and 526 can be different service types or the same service types. As described above, each service type can be a fixed or mobile communications service provided by the IMS network 102. In the illustrated embodiment, a second persona profile 528 branches from the third service type 524. The second persona profile 528 can be assigned to one or more PUIDs that can be used a billable item for that service type, for example.

Like account A 510, the illustrated account B 512 branches to two sub-accounts, in particular, a third sub-account 530 and a fourth sub-account 532. The third sub-account 530 branches to two persona profiles, a third persona profile 534 and a fourth persona profile 536. The persona profiles 534, 536 can be viewed as a billable item for any services provided under the selected persona profile. The fourth sub-account 532 branches to a fifth persona profile 538, a fifth service type 540, and a sixth service type 542. The fifth service type 540 can branch to a sixth persona profile 544 and the sixth service type 542 can branch to a seventh persona profile 546. It should be understood that the illustrated service types 540, 542 can be different service types or the same service types.

Referring now to FIG. 6, a network architecture 600 is illustrated, according to an exemplary embodiment of the present disclosure. A UE 110 can include one or more persona profiles 522, 528, 534, 536, 538, 544, 546, for example. In the illustrated example, two persona profiles, persona profile A 522, 528 and persona profile B 534, 536, 538, 544, 546 are illustrated. By way of example and not limitation, persona profile A can include one of the persona profiles illustrated under account A 510 as illustrated in FIG. 5, such as persona profiles 522, 528, and persona profile B can include one of the persona profiles illustrated under account B 508, such as persona profiles 534, 536, 538, 544, 546. An IMS subscriber can select a persona profile and initiate a communication session with the IMS network 102 via an access network 104, 106, 108. The PUID that is associated with the selected persona profile can be inserted into the communication session. Any network element 114 that contributes to the setup, maintenance, and/or teardown of the communication session can generate a CDR and/or raw usage data and sent the CDR to the UDPS 116 for processing. The UDPS 116 can process the data and format the data into a single UUR 400. The UUR 400 can be sent to the charging/rating/routing systems 118, 120. The UUR 400 can be rated and a charge can be routed to the appropriate billing system 122 based upon the PUID that corresponds to the selected persona profile. The billing system 122 can apply the proper subscriber account with the charge, for example, account A 510 or account B 512.

Referring now to FIG. 7, a method 700 for charging and billing based upon a PUID is illustrated, according to some exemplary embodiments of the present disclosure. The method 700 is described with reference to FIG. 6. It should be understood that the steps of the method 700 are not necessarily presented in any particular order and that performance of some or all the steps in an alternative order(s) is possible and is contemplated. The steps have been presented in the demonstrated order for ease of description and illustration. Steps can be added, omitted and/or performed simultaneously without departing from the scope of the appended claims. It should also be understood that the illustrated process 700 can be ended at any time. Some or all steps of this process, and/or substantially equivalent steps, can be performed by execution of computer-readable instructions stored on a computer-readable memory.

The illustrated method 700 begins and flow proceeds to block 702, wherein a persona profile, such as one of the persona profiles illustrated in FIG. 6 and described immediately above, is selected on a UE 110. Selection of a persona profile can instruct the UE 110 to initiate any future communication sessions with the IMS network 102 using the PUID that is associated with the selected persona profile. By way of example and not limitation, the selected persona profile can be persona profile A 522, 528 or persona profile B 534, 536, 538, 544, 546, as illustrated in FIG. 5 and FIG. 6. Accordingly, as illustrated in block 704, the UE 110 initiates a communication session with the IMS network 102. At block 706, the PUID, for example, PUID-A identifying a persona profile associated with account A 510, can be inserted into the originating communication session record. As the communication session is active, each network element 114, if applicable, can generate a CDR, as illustrated in block 708. The CDRs generated by the network elements 114 can be sent to the UDPS 116. The UPDS 116 can aggregate the CDRs into a UUR 400, as illustrated in block 710. At block 712, the UUR 400 can be sent to the charging and rating systems 118. A rating module can determine the rate at which to charge for the service(s) provided as identified by the UUR 400 and the charging and rating systems 118 can generate a charge, at block 714. At block 716, the charging and rating system 118 can send the charge to the router 122. The router 122 can analyze the charge and route the charge to the appropriate billing system 122 based upon the PUID, for example PUID-A or PUID-B, at block 718. At block 720, the billing system 122 receives the charge and posts the charge to the account associated with the PUID, account A 510 or account B 512, for example. The billing system 122 can generate an invoice reflecting the charges and send the invoice to the customer 502 via any known method of invoice delivery, at block 722. The method 700 can end.

The law does not require and it is economically prohibitive to illustrate and teach every possible embodiment of the present claims. Hence, the above-described embodiments are merely exemplary illustrations of implementations set forth for a clear understanding of the principles of the disclosure. Variations, modifications, and combinations may be made to the above-described embodiments without departing from the scope of the claims. All such variations, modifications, and combinations are included herein by the scope of this disclosure and the following claims. 

The invention claimed is:
 1. A computer-readable memory device storing instructions that, when executed, cause a wireless device to perform operations comprising: receiving first user input at a user interface displayed by the wireless device, the wireless device configured to access a communication service and store data associated with a plurality of usage profiles, the first user input selecting a first usage profile of the plurality of usage profiles, wherein the first usage profile of the plurality of usage profiles corresponds to a first service related to accessing a wireless access network, and wherein a second usage profile of the plurality of usage profiles corresponds to a second service distinct from the first service and related to accessing a packet switching access network; and after selection of the first usage profile and in response to receipt of second user input to initiate a particular communication service: generating a message associated with usage profile-related information corresponding to the first usage profile, the message indicating that usage of the communication service is to be billed to a first billing account of a plurality of billing accounts associated with the wireless device; and sending, from the wireless device, via a wireless network, the message directed to a network element to initiate a communication session at the wireless device, wherein the message includes an identifier that is associated with the usage profile-related information.
 2. The computer-readable memory device of claim 1, wherein the usage profile-related information indicates whether the usage of the communication service is work usage or personal usage.
 3. The computer-readable memory device of claim 1, wherein the usage profile-related information is independent of a subscriber identity module within the wireless device, the subscriber identity module corresponding to the communication service.
 4. The computer-readable memory device of claim 3, wherein the subscriber identity module is operable for use in a connection with each of the plurality of billing accounts.
 5. The computer-readable memory device of claim 1, wherein the first billing account comprises a work account.
 6. The computer-readable memory device of claim 5, wherein the plurality of billing accounts includes the work account and further includes a personal account.
 7. The computer-readable memory device of claim 1, wherein the wireless network comprises an internet protocol network and wherein the message comprises an internet protocol message.
 8. The computer-readable memory device of claim 1, wherein the message is associated with a voice call.
 9. The computer-readable memory device of claim 1, wherein the message comprises a voice over internet protocol message.
 10. The computer-readable memory device of claim 1, wherein the wireless device comprises a mobile phone.
 11. The computer-readable memory device of claim 1, wherein the wireless device comprises a computer.
 12. The computer-readable memory device of claim 1, wherein the wireless device comprises a hand-held device.
 13. The computer-readable memory device of claim 1, wherein the operations further comprise: generating, at the wireless device, a second message associated with second usage profile-related information, the second message indicating that usage of the communication service is to be billed to a second billing account of the plurality of billing accounts; and sending the second message from the wireless device via the wireless network.
 14. A wireless device comprising: a network interface configured to access a communication service via a wireless network; a processor; and a memory storing data associated with a plurality of usage profiles and storing instructions that, when executed by the processor, cause the processor to perform operations comprising: receiving, at a displayed user interface, a first selection of a first usage profile of the plurality of usage profiles, wherein the first usage profile corresponds to a first service related to accessing a wireless access network, and wherein a second usage profile of the plurality of usage profiles corresponds to a second service distinct from the first service and related to accessing a packet switching access network; and after receiving the first selection and in response to receipt of user input to initiate a particular communication service: generating a first message associated with usage profile-related information corresponding to the first usage profile, the first message indicating that usage of the communication service is to be billed to a first billing account; and sending the first message via the network interface, the first message directed to a network element to initiate a communication session at the wireless device, wherein the first message includes an identifier that is associated with the first usage profile-related information.
 15. The wireless device of claim 14, wherein the wireless device comprises a mobile phone.
 16. The wireless device of claim 14, wherein the wireless device comprises a computer.
 17. A method comprising: receiving first user input at a user interface displayed by a wireless device, the wireless device configured to access a communication service and store data associated with a plurality of usage profiles, the first user input selecting a first usage profile of the plurality of usage profiles, wherein the first usage profile corresponds to a first service related to accessing a wireless access network, and wherein a second usage profile of the plurality of usage profiles corresponds to a second service distinct from the first service and related to accessing a packet switching access network; and after selection of the first usage profile and in response to receipt of second user input to initiate a particular communication service: generating a message associated with usage profile-related information corresponding to the first usage profile, the message indicating that usage of the communication service is to be billed to a first billing account of a plurality of billing accounts associated with the wireless device; and sending, from the wireless device, via a wireless network, the message directed to a network element to initiate a communication session at the wireless device, wherein the message includes an identifier that is associated with the usage profile-related information.
 18. The method of claim 17, wherein the plurality of billing accounts includes a work account and a personal account.
 19. The method of claim 17, wherein the usage profile-related information indicates whether the usage of the communication service is work usage or personal usage.
 20. The wireless device of claim 14, wherein the usage profile-related information indicates whether the usage of the communication service is work usage or personal usage. 